Design verification by symbolic simulation using a native hardware description language

ABSTRACT

A method and apparatus for performing design verification is described. In one embodiment, a method for performing design verification includes specifying at least one object that represents at least one signal as a symbol in a design using a first command and instructing a symbolic simulator with the first command to treat the at least one object as a symbol.

FIELD OF THE INVENTION

[0001] The present invention relates to the field of design simulation and verification; more particularly, the present invention relates to augmenting design descriptions to perform design verification by symbolic simulation.

BACKGROUND OF THE INVENTION

[0002] The sophistication of modern integrated circuit (IC) design means that designers have to rely on automation tools (ICDA) to manage the complexity. Over the past two decades, new tools have continually been developed to increase the level of automation and enable designers to develop increasingly complex and powerful IC products.

[0003] The increasing demand for new IC design tools is fueled by rapidly changing IC fabrication process technology. As IC feature sizes shrink to dimensions of 0.25 micron and smaller, the complexity of the designs (number of devices on a single chip) drives the need for improved techniques to design and verify the required functionality.

[0004] The continuing increase in IC design complexity, along with the lack of specific automation tools, has led to design verification becoming a major design bottleneck.

[0005] There are a number of alternatives currently being used to reduce the verification bottleneck. These include both dynamic and static verification. Dynamic verification is the standard approach to verification. Recent advances in dynamic verification can be categorized into two categories: testbench management and augmented verification techniques.

[0006] Testbench management tools abstract the creation of test vectors to a higher level. These tools provide a language to help an individual create tests and measurement tools to help the individual quantify how good coverage is. Testbench management has a number of advantages that include providing an evolutionary step to the problem of design verification, automating many of the repetitive tasks and helps the designer focus on the problem of what to test, and providing a way of reducing the ambiguity of the test specification. Testbench management provides a number of disadvantages which include being based on the continued use of digital or binary simulation and large numbers of test vectors, forcing a designer to use a proprietary test language to express tests, and having non-simplified debugging.

[0007] Augmented verification techniques can be used with existing approaches and testbench management tools. Testbench management tools provide some augmented verification techniques, but these augmented techniques seek to improve measurement and increase test coverage. The use of augmented verification techniques is advantageous in that it provides an evolutionary step to the problem of design verification, improves the observability of the tests, and automates some of the steps of test creation to improve the scope of testing. The disadvantages of augmented verification techniques include being based on the use of binary simulation and large numbers of vectors, forcing a designer to use a proprietary methodology, and having no guarantee that the tests will catch all problems.

[0008] Static verification is a new technology that attempts to formally prove that a design meets its specifications.

[0009] Other verification techniques include equivalence checking which compares two gate level netlists is fairly established and its benefits are not an issue. However, application of the same formal techniques to compare RTL or behavior against a specification is still problematic. Model checking (behavior/RTL-RTL/gate checking) is still in the very early stages of use. Its inherent limitation of a maximum of about 200 registers means that model checking has very limited use without extensive engineering effort.

[0010] The advantages of this approach include providing exhaustive and conclusive proof that the design is correct, managing non-linear growth in design size, and providing rapid response and precise debugging. The disadvantages of this approach include having technical limitations such that it is only appropriate for a very small number of designs, very hard for engineers to grasp, and demands substantial reworking of design capture techniques.

[0011] Both dynamic and static approaches have merit; however, there is an immediate problem that neither approach can solve today. Until now, there has been no adequate solution to the growing crisis of design verification. Existing simulation techniques are not able to keep up with complexity growth. Formal techniques have too many restrictions and functional verification is the major cause of problems in a design project. Therefore, a need exists to provide an improved simulation technique that reduces the number of restrictions that currently exist in a design project.

SUMMARY OF THE INVENTION

[0012] A method and apparatus for performing design verification is described. In one embodiment, a method for performing design verification includes specifying at least one object that represents at least one signal as a symbol in a design using a first programming interface call and instructing a symbolic simulator with the first programming interface call to treat the at least one object as a symbol.

BRIEF DESCRIPTION OF THE DRAWINGS

[0013] The present invention will be understood more fully from the detailed description given below and from the accompanying drawings of various embodiments of the invention, which, however, should not be taken to limit the invention to the specific embodiments, but are for explanation and understanding only.

[0014]FIG. 1 is a flow diagram of one embodiment of a process for verifying a design.

[0015]FIG. 2 is a block diagram of a circuit showing symbolic simulation propagating symbols in logic expressions.

[0016]FIG. 3 is an exemplary arithmetic logic unit.

DETAILED DESCRIPTION OF THE PRESENT INVENTION

[0017] A method and apparatus for improved design verification is described. In the following description, numerous details are set forth. It will be apparent, however, to one skilled in the art, that the present invention may be practiced without these specific details. In other instances, well-known structures and devices are shown in block diagram form, rather than in detail, in order to avoid obscuring the present invention.

[0018] Some portions of the detailed descriptions that follow are presented in terms of algorithms and symbolic representations of operations on data bits within a computer memory. These algorithmic descriptions and representations are the means used by those skilled in the data processing arts to most effectively convey the substance of their work to others skilled in the art. An algorithm is here, and generally, conceived to be a self-consistent sequence of steps leading to a desired result. The steps are those requiring physical manipulations of physical quantities. Usually, though not necessarily, these quantities take the form of electrical or magnetic signals capable of being stored, transferred, combined, compared, and otherwise manipulated. It has proven convenient at times, principally for reasons of common usage, to refer to these signals as bits, values, elements, symbols, characters, terms, numbers, or the like.

[0019] It should be borne in mind, however, that all of these and similar terms are to be associated with the appropriate physical quantities and are merely convenient labels applied to these quantities. Unless specifically stated otherwise as apparent from the following discussion, it is appreciated that throughout the description, discussions utilizing terms such as “processing” or “computing” or “calculating” or “determining” or “displaying” or the like, refer to the action and processes of a computer system, or similar electronic computing device, that manipulates and transforms data represented as physical (electronic) quantities within the computer system's registers and memories into other data similarly represented as physical quantities within the computer system memories or registers or other such information storage, transmission or display devices.

[0020] The present invention also relates to apparatus for performing the operations herein. This apparatus may be specially constructed for the required purposes, or it may comprise a general purpose computer selectively activated or reconfigured by a computer program stored in the computer. Such a computer program may be stored in a computer readable storage medium, such as, but is not limited to, any type of disk including floppy disks, optical disks, CD-ROMs, and magnetic-optical disks, read-only memories (ROMs), random access memories (RAMs), EPROMs, EEPROMs, magnetic or optical cards, or any type of media suitable for storing electronic instructions, and each coupled to a computer system bus.

[0021] The algorithms and displays presented herein are not inherently related to any particular computer or other apparatus. Various general purpose systems may be used with programs in accordance with the teachings herein, or it may prove convenient to construct more specialized apparatus to perform the required method steps. The required structure for a variety of these systems will appear from the description below. In addition, the present invention is not described with reference to any particular programming language. It will be appreciated that a variety of programming languages may be used to implement the teachings of the invention as described herein.

[0022] Overview

[0023] The present invention allows hardware description languages that are normally used to describe designs to be used in symbolic simulators. The present invention allows this instructing the symbolic simulator to treat one or more specified signals (e.g., inputs) as symbolic.

[0024] In one embodiment, the simulator is instructed through the use of one or more programming commands, or statements, (e.g., programming interface calls (PLIs)) that declare certain variables as symbols. That is, a command may be used to indicate to the simulator that an object in a hardware description language used to indicate a signal (e.g., a Verilog object) is to be a symbol to the simulator, such that variable assigned objects are designated as symbolic variable objects. In this manner, the existing hardware description languages are able to support the specification of symbolic input. Upon encountering such a programming statement, the symbolic simulator propagates logic expressions, instead of binary values, capturing the relationship from input to output.

[0025] The present invention permits a check to be inserted to perform a complete test and generate information allowing the re-creation of any identified fault. In one embodiment, the simulator is instructed to perform the check through the use of one or more programming statements that generate a file of one or more vectors (e.g., binary vectors) that may be used to locate any identified fault, thereby simplifying debug. Once an error has been identified, well-known simulators that employ binary numbers may be used to isolate the fault.

[0026] By using symbolic simulation, in one simulation run, many combinations of binary simulation runs are achieved to verify the design, such that the simulator verifies the complete behavior of a design in a more efficient manner than traditional simulation.

[0027] Design Verification Flow

[0028]FIG. 1 is a flow diagram of one embodiment of a process comprising a series of processing steps to simulate a design. The process may be performed by processing logic which may comprise software, hardware or a combination of both.

[0029] Referring to FIG. 1, the process augments a design to specify to the simulator the signals to treat as symbolic (processing block 101). The signals may be inputs, interrupts, memory values, or any other portion of a design that may be represented as an object in a hardware description language.

[0030] In one embodiment, the input engine of the simulator accepts a Verilog netlist of a block and the users instructs the simulator to run with one, more or all inputs symbolically. In such a case, the user may specify which inputs using a programming language interface (PLI) command which is inserted into the design flow. Other languages may have other similar mechanisms to the PLIs, such as for example using an API in HDL, and may be used in the same manner.

[0031] In one embodiment, the process instructs the simulator using the following PLI command:

[0032] $esp_var(a, b, . . . )

[0033] which causes the simulator to designate the objects a, b, etc. as symbols. In one embodiment, any number of objects may be listed in the PLI command. A symbol database may be used to keep track of the definitions of each symbol.

[0034] Then, the process compiles the design description (processing block 102). During compile, the symbolic variables are recognized, via the PLIs, and an internal intermediary structure for the symbolic simulator.

[0035] Next, the process performs symbolic simulation (processing block 103). Symbolic simulation allows the designer to add symbols to existing binary values (0, 1, X and Z) during simulation. When the simulator detects symbol input, it propagates a boolean expression instead of propagating the digital value that is the result of the logical operation on the inputs. As the expressions are propagated, they capture the input/output mapping for all possible conditions. Although the final output expression may be very lengthy, they can readily be used to check against specified assertions or to compare against a reference model, particularly where the reference model is in symbolic format as well. By using symbols, one is able to fully verify a block without having to select a set of values. FIG. 2 illustrates an example of expressions being propagated from the input to the output of a design.

[0036] While performing symbolic simulation, the simulator is instructed to make checks to validate the functionality of the design. In one embodiment, another PLI command is inserted into the design specification in order to instruct the simulator to detect faults. If the design specification is in Verilog, one embodiment of the PLI command may be as follows:

[0037] $esp_error( )

[0038] which generates a file with the binary vector needed to locate the fault (so that debugging is implied.) In one embodiment, the file comprises binary value assignments for those symbolic variables declared by $esp_var.

[0039] After performing symbolic simulation, the process performs determines whether any error PLI (i.e., $esp_error) was executed (processing block 103). If no error PLI was executed, the process ends. If an error PLI was executed, the process generates a file, referred to herein as “esp_testvector”, which includes the variable assignments (processing block 104). Then, based on the contents of the file, the process replays or uses a binary simulator environment to handle any faults.

[0040] An Exemplary Application

[0041] An exemplary circuit is shown in FIG. 3. Considering the testbench required to run the simulation, the following is given:

[0042] module test_bench( );

[0043] reg [15:0] A, B, O32;

[0044] reg CI;

[0045] reg [3:0] INST;

[0046] wire CO;

[0047] reg [31:0] a,b

[0048] reg [3:0] i;

[0049] wire [15:0] out;

[0050] DUT ALU (A,B,INST,CLK,out, CO);

[0051] initial begin

[0052] $esp_var (a,b,i);

[0053] A=a[15:0];

[0054] B=b[15:0];

[0055] CI=1′b0;

[0056] INST=i;

[0057] # cycle

[0058] O32 [15:0]=out;

[0059] A=a [31:16];

[0060] B=b [31:16];

[0061] CI=CO;

[0062] # cycle

[0063] O32 [31:16]=out

[0064] if ((INST==4′b0100) & ({CO, O32} !==(a+b))) / / addition checking begin

[0065] $display(“ALU ERROR: addition error is detected”);

[0066] $esp_error(“Binary vector is created for error detection”);

[0067] end

[0068] end

[0069] endmodule

[0070] In the case of the ALU, it is possible to run one symbolic test vector sweep and fully verify the block. The $esp_var command instructs the simulator to interpret the variables as symbolic and, using a series of assert statements, the user can verify the functionality for every possible combination of input values. Additionally, there are a set of debugging commands, $display( ) and $esp_error( ), that will help track and eliminate bugs that symbolic simulation has highlighted.

[0071] Because of the use of the added commands, an individual does not have to spend any time deciding a set of input values, symbolic vectors cover every and all possible combinations. So, if no bugs are detected, the tester can have confidence that there is no combination of values that will cause an error to occur.

[0072] In one embodiment, all of the inputs are not treated symbolically. This may be the result of too little or unacceptable memory usage. The user may be allowed to select which inputs require the use symbols. In an alternative embodiment, the testing engine randomly selects symbols. The selection may be based on ensuring that the simulation finishes. The user is notified of which signals were associated with symbols.

[0073] In one embodiment, the simulator accepts Verilog behavior, RTL, gate and transistor level inputs and works with most standard PLI routines. In one embodiment, a SPICE netlist is converted to a Verilog switch level netlist. In such a case, the symbolic simulator runs symbolic simulation on the transistor level netlist and compares the results with and RTL description. Thus, if using self-checking or reference models in Verilog, there is very little change required to use symbolic simulation.

[0074] Whereas many alterations and modifications of the present invention will no doubt become apparent to a person of ordinary skill in the art after having read the foregoing description, it is to be understood that any particular embodiment shown and described by way of illustration is in no way intended to be considered limiting. Therefore, references to details of various embodiments are not intended to limit the scope of the claims which in themselves recite only those features regarded as essential to the invention.

[0075] Thus, a method and apparatus for improved design verification has been described. 

I claim:
 1. A method for performing design verification, the method comprising: specifying at least one object that represents at least one signal as a symbol in a design using a first programming interface call (PLI) command; and instructing a symbolic simulator with the first command to treat the at least one object as a symbol.
 2. The method defined in claim 1 further comprising: inserting the first command into a design specification; and inputting the design specification into the symbolic simulator.
 3. The method defined in claim 1 wherein the at least one object comprise a hardware description language object.
 4. The method defined in claim 1 wherein the at least one object comprises a Verilog object.
 5. The method defined in claim 1 wherein the first command comprises a Programming Language Interface (PLI).
 6. The method defined in claim 1 wherein the at least one signal comprises an input.
 7. The method defined in claim 1 further comprising: specifying a check using a second command, the check to perform a test to validate design functionality; and instructing the symbolic simulator using the second command to perform the test.
 8. The method defined in claim 7 further comprising: inserting the first and second commands into a design specification; and inputting the design specification into the symbolic simulator.
 9. The method defined in claim 7 wherein the second command comprises a PLI.
 10. The method defined in claim 7 further comprising: instructing the symbolic simulator to generate a file with information to locate an identified fault.
 11. An article of manufacture having at least one recordable medium having stored thereon executable instructions which, when executed by at least one processing device, cause the at least one processing device to: specify at least one object that represents at least one signal as a symbol in a design using a first command; and instruct a symbolic simulator with the first command to treat the at least one object as a symbol.
 12. The article of manufacture defined in claim 11 further comprising executable instructions stored on the at least one recordable medium which, when executed by at least one processing device, cause the at least one processing device to: insert the first command into a design specification; and input the design specification into the symbolic simulator.
 13. The article of manufacture defined in claim 11 wherein the at least one object comprise a hardware description language object.
 14. The article of manufacture defined in claim 11 wherein the at least one object comprises a Verilog object.
 15. The article of manufacture defined in claim 11 wherein the first command comprises a Programming Language Interface (PLI).
 16. The article of manufacture defined in claim 11 wherein the at least one signal comprises an input.
 17. The article of manufacture defined in claim 11 further comprising executable instructions stored on the at least one recordable medium which, when executed by at least one processing device, cause the at least one processing device to: specify a check using a second command, the check to perform a test to validate design functionality; and instruct the symbolic simulator using the second command to perform the test.
 18. The article of manufacture defined in claim 17 further comprising executable instructions stored on the at least one recordable medium which, when executed by at least one processing device, cause the at least one processing device to: insert the first and second commands into a design specification; and input the design specification into the symbolic simulator.
 19. The article of manufacture defined in claim 17 wherein the second command comprises a PLI.
 20. The article of manufacture defined in claim 17 further comprising executable instructions stored on the at least one recordable medium which, when executed by at least one processing device, cause the at least one processing device to: instruct the symbolic simulator to generate a file with information to locate an identified fault. 